Ownership
The user who installs the Fleek Network Lightning CLI matters, as it can own or delegate ownership of the dependencies and applications being installed.
For example, if you have followed the install document recommendations and have:
- Created a user lgtn
- Switched to the user lgtn
- Executed the installation process as lgtn
The username can be anything, we are using the term lgtn as the example provided throughout our documentation. Select your username in accordance to your preferences.
You'll find that it owns the following directories under the user home (/home/lgtn):
drwxr-x--- 6 lgtn lgtn 4096 Sep 12 10:27 .
drwxr-xr-x 3 root root 4096 Sep 11 12:28 ..
drwxrwxr-x 5 lgtn lgtn 4096 Sep 11 12:29 .cargo
drwxrwxr-x 5 lgtn lgtn 4096 Sep 11 15:25 .lightning
drwxrwxr-x 6 lgtn lgtn 4096 Sep 11 12:29 .rustup
drwxrwxr-x 3 lgtn lgtn 4096 Sep 11 12:28 fleek-network
Above, we have the listing properties set as drwxrwxr-x and the ownership lgtn:lgtn.
On the other hand, if you have done the installation process as root superuser, you'll find that:
- The location of the directories and files goes under the
/rootpathname - The ownership is set to root:root
Learn more about file permissions from the Linux Foundation.
To learn more about file permission on Linux, read the Understanding Linux File Permissions.
Using sudo to delegate permissions
Consider file ownership and permissions to understand where the keystore is located. Take close attention when executing commands as an admin–with or without super user (root) or sudo.
If a command is executed without sudo then the generated output goes onto the user home.
lgtn keys generate
Resulting in having the keystore saved onto /home/username/.lightning/keystore.
On the other hand, if a command is executed with sudo then the generated output is delegated to root directory.
sudo lgtn keys generate
Resulting in having the keystore saved onto /root/.lightning/keystore.
User $HOME directory
The home directory is a directory that contains the personal files of a particular user of the system. On Linux, the $HOME environment variable is set by the login program, which sets the user `$HOME`` accordingly. A user's home goes by the username, the user who's logged in.
For this reason, a user can change to the home directory by executing:
cd $HOME
A shorthand allows a user to refer to their home directory simply as ~ (tilde), as follows:
cd ~
We can find that the HOME or ~ (tilde) is highly dependent on the user who's logged in. Since we know that the user might delegate to root by the usage of sudo, this can help troubleshoot and explain the location of our files e.g. the keystore. In the section Set the locations of the user paths, we learn how to define the location of our user configuration paths to avoid confusion. By doing it we ensure that when running the service, the service picks the correct configuration paths for our user.
To learn more about the user $HOME directory read the wikipedia Home directory document.
Set the locations of the user paths
In the /home/<USERNAME>/.lightning/config.toml you'll find some and more of the following:
[BLANK]
[application]
db_path = "~/.lightning/data/app_db"
[consensus]
store_path = "~/.lightning/data/narwhal_store"
[fsstore]
root = "~/.lightning/blockstore"
[resolver]
store_path = "~/.lightning/data/resolver_store"
[signer]
consensus_key_path = "~/.lightning/keystore/consensus.pem"
node_key_path = "~/.lightning/keystore/node.pem"
The configuration properties and values presented above are a shorter version of what you'll find on your configuration.toml. We keep it short to make it easier to follow, do not copy and paste.
Find and replace all instances of ~ in the config file /home/<USERNAME>/.lightning/config.toml.
Here's an example of how to do it using sed:
sed -i "s|~/.lightning|/home/<USERNAME>/.lightning|g" "/home/<USERNAME>/.lightning/config.toml"
Replace the <USERNAME> with your username. For example, if you have followed the recommendation to create a user it would look like /home/lgtn/.lightning/config.toml for the username lgtn.
For example, if your username is lgtn that'd look like this:
sed -i "s|~/.lightning|/home/lgtn/.lightning|g" "/home/lgtn/.lightning/config.toml"
Once modified, you can run a cat to see the content of the files to confirm it has been updated.
cat /home/lgtn/.lightning/config.toml
For our example where we opted in for the username lgtn that would look like:
[BLANK]
[application]
db_path = "~/.lightning/data/app_db"
[consensus]
store_path = "~/.lightning/data/narwhal_store"
[fsstore]
root = "~/.lightning/blockstore"
[resolver]
store_path = "~/.lightning/data/resolver_store"
[signer]
consensus_key_path = "~/.lightning/keystore/consensus.pem"
node_key_path = "~/.lightning/keystore/node.pem"
Bear in mind that we are keeping the content of the file short to make it easier to read and follow. The content of your configuration file should look slightly different, amongst these it should contain other properties and values. You should not copy and replace the content of your files with the ones presented here.
Set the configuration flag -c on the service unit file
The following section assumes that a System service unit has been declared, and you're using systemctl to control the service, as described in our Systemd Service Setup install section.
Open and edit the /etc/systemd/system/lightning.service file.
-
Replace
<USERNAME>with YOUR username. For example, in the documentation we use the username lgtn, which means we'd replace<USERNAME>withlgtn. -
Make sure that the ExecStart is set correctly, including the
-c
[Unit]
Description=Fleek Network Node lightning service
[Service]
Type=simple
MemoryHigh=32G
RestartSec=15s
Restart=always
ExecStart=lgtn -c /home/<USERNAME>/.lightning/config.toml run
StandardOutput=append:/var/log/lightning/output.log
StandardError=append:/var/log/lightning/diagnostic.log
Environment=TMPDIR=/var/tmp
[Install]
WantedBy=multi-user.target
For our example, as the username lgtn it would look like:
[Unit]
Description=Fleek Network Node lightning service
[Service]
Type=simple
MemoryHigh=32G
RestartSec=15s
Restart=always
ExecStart=lgtn -c /home/lgtn/.lightning/config.toml run
StandardOutput=append:/var/log/lightning/output.log
StandardError=append:/var/log/lightning/diagnostic.log
Environment=/var/tmp
[Install]
WantedBy=multi-user.target
When complete make sure the file is saved and the systemctl daemon is reloaded, as follows:
sudo systemctl daemon-reload
Consequently, when a user manages the service via the systemctl, the Lightning CLI process will read the configuration file settings provided above. It includes the location of the user preferences, such as the keystore location amongst others, preventing confusion regardless of root delegation.
